Record the ast of uses and imports #188
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
|
I have update the branch to avoid the adding the implicit name metadata as it parses. |
arielb1
pushed a commit
to arielb1/rust
that referenced
this pull request
Apr 10, 2015
Improve the issue reference format in headers.
oli-obk
added a commit
to oli-obk/rust
that referenced
this pull request
Jul 19, 2017
Bail out on overflow
keeperofdakeys
pushed a commit
to keeperofdakeys/rust
that referenced
this pull request
Dec 12, 2017
Roll together a few PRs in the queue
dlrobertson
pushed a commit
to dlrobertson/rust
that referenced
this pull request
Nov 29, 2018
Moar trait object verbiage.
matthiaskrgr
pushed a commit
to matthiaskrgr/rust
that referenced
this pull request
Mar 7, 2023
celinval
pushed a commit
to celinval/rust-dev
that referenced
this pull request
Jun 4, 2024
Handle duplicate dynamic trait names correctly, for now keeping the string-matching based vtable implementation. In the generated vtable itself, use the function name scoped to the specific trait (A::foo vs B::foo) instead of just the function name. Merge some vtable lookup handling. Add tests for more potential naming conflicts.
carolynzech
pushed a commit
to celinval/rust-dev
that referenced
this pull request
Dec 9, 2024
…nd `byte_offset` (rust-lang#188) Towards rust-lang#76 This pull request impelments proof for contracts for `byte_add`, `byte_sub` and `byte_offset` for `<dyn Trait>`. Both `const` and `mut` versions are included. It serves as an addition to an existing [PR](model-checking#169) but is submitted separately to avoid disrupting the ongoing review process for that PR. --------- Co-authored-by: Surya Togaru <[email protected]> Co-authored-by: stogaru <[email protected]> Co-authored-by: Felipe R. Monteiro <[email protected]>
This pull request was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Some points I would really like some feedback on
Do we have a better name for "use or import" than "use_or_import" :-)
Is
use foo;
import foo.bar;
use zed;
legal or should we require that all uses come first?